When I try to view Object Properties in the standard view, I get the following DXL error: |
Re: DXL Errors whe opening Object Properties >Louie |
Re: DXL Errors whe opening Object Properties llandale - Thu Apr 02 14:51:48 EDT 2009 Hi Louie,
I am also having same issue with 100 of modules in a folder.
-R-E- DXL: <standard/itemProperties/linkSetsTab.inc:193> null Module name parameter was passed into argument position 2
It is not possible to open each and every module and check the DXL attribute and correct the syntax. Could you please help me with a dxl script which I can run on the folder to get all DXL based attributes in all the modules in a folder.
Regards, Sousan |
Re: DXL Errors whe opening Object Properties sousan - Fri Apr 26 07:02:18 EDT 2019 Hi Louie,
I am also having same issue with 100 of modules in a folder.
-R-E- DXL: <standard/itemProperties/linkSetsTab.inc:193> null Module name parameter was passed into argument position 2
It is not possible to open each and every module and check the DXL attribute and correct the syntax. Could you please help me with a dxl script which I can run on the folder to get all DXL based attributes in all the modules in a folder.
Regards, Sousan In my 2009 post I concluded it was Attr-DXL because the DXL errors said it was in a "Line" (-R-E- DXL: <Line:16>) and did not attempt to specify any file name (-R-E- DXL: <standard/itemProperties/linkSetsTab.inc:193>) as in your errors. Since opening the object properties will indeed run any Attr-DXL for that object (so it can display the value in the Properties dialog), I concluded that's where the error was. Some supporting facts: o Deployed Native DXL has lots of comments at the top and do not give errors with low numbered lines like 16. o It is a "Run time" error because of the "-R-E-". If it were an interpret error like bad syntax you would have gotten errors when you opened the module.
I would close all modules including using the Tools>Manage Open Modules.. dialog. Then try again. If it fails then restart DOORS. If it fails again then I'd suspect you have some database corruption and will need your IT folks to run the "Integrity Checker" (I think). On 2nd thought, you would indeed get this error if some Attr-DXL was so rotten that it closed the module, the "current Module". So look through the Attr-DXL code for the word "close". It is possible the "close" of a module looks benign (such as at the end of a link), but if this module is linked to itself it would, well, close itself. On 3rd thought, since the error is while building the "LinkSet" ("pairing") tab, you have some issues in the Folder's Linkset Pairings. Open a module, ignore the error, goto the LinkSets tab and try to find some offending Pairing and delete it. You will probably though need some DXL browsing the folder's "LinkModuleDescriptor"s and providing some mechanism for deleting a corrupt one. I wonder what happens if there is an LSP for a target module for which you lack even "R" access. Have the "Administrator" open these modules and see if that account gets the errors.
-Louie |
Re: DXL Errors whe opening Object Properties llandale - Fri Apr 26 20:03:19 EDT 2019 In my 2009 post I concluded it was Attr-DXL because the DXL errors said it was in a "Line" (-R-E- DXL: <Line:16>) and did not attempt to specify any file name (-R-E- DXL: <standard/itemProperties/linkSetsTab.inc:193>) as in your errors. Since opening the object properties will indeed run any Attr-DXL for that object (so it can display the value in the Properties dialog), I concluded that's where the error was. Some supporting facts: o Deployed Native DXL has lots of comments at the top and do not give errors with low numbered lines like 16. o It is a "Run time" error because of the "-R-E-". If it were an interpret error like bad syntax you would have gotten errors when you opened the module.
I would close all modules including using the Tools>Manage Open Modules.. dialog. Then try again. If it fails then restart DOORS. If it fails again then I'd suspect you have some database corruption and will need your IT folks to run the "Integrity Checker" (I think). On 2nd thought, you would indeed get this error if some Attr-DXL was so rotten that it closed the module, the "current Module". So look through the Attr-DXL code for the word "close". It is possible the "close" of a module looks benign (such as at the end of a link), but if this module is linked to itself it would, well, close itself. On 3rd thought, since the error is while building the "LinkSet" ("pairing") tab, you have some issues in the Folder's Linkset Pairings. Open a module, ignore the error, goto the LinkSets tab and try to find some offending Pairing and delete it. You will probably though need some DXL browsing the folder's "LinkModuleDescriptor"s and providing some mechanism for deleting a corrupt one. I wonder what happens if there is an LSP for a target module for which you lack even "R" access. Have the "Administrator" open these modules and see if that account gets the errors.
-Louie Hi Louie, Thank you so much for your prompt answer. :) I did an integrity check and found couple of missing project reference. after fixing the references error is not appearing.
Regards, Sousan |